Decoupling service and network provider identification in wireless communications

ABSTRACT

Aspects described herein relate to detecting wireless network services. A network identifier can be determined in a broadcast message received from a network entity, and a connection with a network related to the network entity can be established based at least in part on the network identifier. Using the connection, the network entity can be queried for information related to services available at the network, where the information may indicate one or more subscription providers related to the services.

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

The present application for patent claims priority to ProvisionalApplication No. 61/972,025 entitled “APPARATUS AND METHOD FOR DECOUPLEDSERVICE AND NETWORK PROVIDER IDENTIFICATION” filed Mar. 28, 2014, whichis assigned to the assignee hereof and hereby expressly incorporated byreference herein.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustypes of communication content such as voice, data, and so on. Thesesystems may be multiple-access systems capable of supportingcommunication with multiple users by sharing the available systemresources (e.g., bandwidth and transmit power). Examples of suchmultiple-access systems include code division multiple access (CDMA)systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, 3GPP Long Term Evolution (LTE)systems, and orthogonal frequency division multiple access (OFDMA)systems.

Generally, a wireless multiple-access communication system cansimultaneously support communication for multiple user equipment devices(UE). Each UE communicates with one or more base stations, such as anevolved Node B (eNB) via transmissions on the forward and reverse links.The forward link (or downlink) refers to the communication link from theeNBs to the UEs, and the reverse link (or uplink) refers to thecommunication link from the UEs to the eNBs. This communication link maybe established via a single-in-single-out, multiple-in-single-out or amultiple-in-multiple-out (MIMO) system. In this regard, the UEs canaccess wireless network via one or more eNBs.

Network deployment for these systems is typically fixed, and thus theeNBs communicate with a home network related to a UE to obtain and/orverify subscription information for the UE on a given network. Wirelessnetworks typically employ a home subscriber server (HSS) for managinginformation relating to UEs subscriber to the wireless network, whichmay be based on identifying the UE using its international mobilesubscriber identifier (IMSI) and/or other identification. In thisregard, eNBs providing wireless network access to a UE can communicatewith the UE's HSS (e.g., by traversing one or more network nodes) toverify the UE's subscription. In many examples, the eNB can be on avisiting network and can access the HSS on the UE's home network toverify the subscription.

There is a desire, however, to allow UEs to communicate using one ormore wireless network technologies in other contexts over third-partynetworks where authentication is managed by an owner of the third-partynetwork and/or where frequency bands in unlicensed spectrums are usedfor communications.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

According to an example, a method for detecting wireless networkservices is provided. The method includes determining a networkidentifier in a broadcast message received from a network entity,establishing a connection with a network related to the network entitybased at least in part on the network identifier, and querying, usingthe connection, the network entity for information related to servicesavailable at the network.

In another example, an apparatus for detecting wireless network servicesis provided. The apparatus includes an identifier determining componentconfigured to determine a network identifier in a broadcast messagereceived from a network entity, a connection establishing componentconfigured to establish a connection with a network related to thenetwork entity based at least in part on the network identifier, and aservice querying component configured to query, using the connection,the network entity for information related to services available at thenetwork.

In yet another example, an apparatus for detecting wireless networkservices is provided. The apparatus includes means for determining anetwork identifier in a broadcast message received from a networkentity, means for establishing a connection with a network related tothe network entity based at least in part on the network identifier, andmeans for querying, using the connection, the network entity forinformation related to services available at the network.

In another example, a computer-readable medium for detecting wirelessnetwork services. The computer-readable medium includes code fordetermining a network identifier in a broadcast message received from anetwork entity, code for establishing a connection with a networkrelated to the network entity at least in part on the networkidentifier, and code for querying, using the connection, the networkentity for information related to services available at the network.

According to an example, a method for advertising wireless networkservices. The method includes broadcasting a message including a networkidentifier, wherein the network identifier indicates a type of network,establishing a connection with one or more user equipments (UEs), andproviding service information to the one or more UEs based at least inpart on a service query.

In another example, an apparatus for advertising wireless networkservices is provided. The apparatus includes an identifier broadcastingcomponent configured to broadcast a message including a networkidentifier, wherein the network identifier indicates a type of network,a connection establishing component configured to establish a connectionwith one or more user equipments (UEs), and a service provisioningcomponent configured to provide service information to the one or moreUEs based at least in part on a service query.

In yet another example, an apparatus for advertising wireless networkservices is provided. The apparatus includes means for broadcasting amessage including a network identifier, wherein the network identifierindicates a type of network, means for establishing a connection withone or more user equipments (UEs), and means for providing serviceinformation to the one or more UEs based at least in part on a servicequery.

In another example, a computer-readable medium for advertising wirelessnetwork services is provided including code for causing at least onecomputer to broadcast a message including a network identifier, whereinthe network identifier indicates a type of network, code for causing theat least one computer to establish a connection with one or more userequipments (UEs), and code for causing the at least one computer toprovide service information to the one or more UEs based at least inpart on a service query.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements.

FIG. 1 illustrates an example system for advertising network services inaccordance with aspects described herein.

FIG. 2 illustrates an example system for offloading wirelesscommunication services in accordance with aspects described herein.

FIG. 3 illustrates an example system for determining available wirelessnetwork services in accordance with aspects described herein.

FIG. 4 illustrates an example method for determining available wirelessnetwork services in accordance with aspects described herein.

FIG. 5 illustrates an example method for advertising available wirelessnetwork services in accordance with aspects described herein.

FIG. 6 illustrates an example system for communicating in a wirelessnetwork to determine available services in accordance with aspectsdescribed herein.

FIG. 7 illustrates an example method for establishing a connection witha network entity in accordance with aspects described herein.

FIG. 8 illustrates an example system for provisioning credentials foraccessing available wireless network services in accordance with aspectsdescribed herein.

FIG. 9 illustrates an example method for obtaining provisionedcredentials for accessing wireless network services in accordance withaspects described herein.

FIG. 10 illustrates an example method for providing credentials foraccessing wireless network services in accordance with aspects describedherein.

FIG. 11 illustrates an example method for providing credentials foraccessing wireless network services in accordance with aspects describedherein.

FIG. 12 illustrates an example system for provisioning credentials foraccessing available wireless network services in accordance with aspectsdescribed herein.

FIG. 13 illustrates an example system for authenticating devices foraccessing available wireless network services in accordance with aspectsdescribed herein.

FIG. 14 illustrates an example method for requesting authentication foraccessing wireless network services in accordance with aspects describedherein.

FIG. 15 illustrates an example method for authenticating devices foraccessing wireless network services in accordance with aspects describedherein.

FIGS. 16 and 17 illustrate example systems for authenticating devicesfor accessing available wireless network services in accordance withaspects described herein.

FIG. 18 illustrates a multiple access wireless communication systemaccording to one embodiment.

FIG. 19 illustrates a block diagram of a communication system.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details.

Described herein are various aspects related to decoupling serviceidentification information and network identification information fornetwork and subscription selection in wireless communications, whichallows one network provider to provide network devices with networkaccess to a network service of a different network provider. The serviceidentification information can include one or more identifiers relatingto a network service offered by a network node, one or more identifiersof a subscription provider related to the network service, etc., suchthat a user equipment (UE) can determine whether and/or how to accessthe network service (e.g., based on credentials corresponding to thesubscription provider, etc.). The network identification information caninclude one or more identifiers of a network provider related to anetwork node that can offer various network services, as describedherein.

In particular, in an example, a network can allow for access using awireless communication service and providing subscription managementwithout requiring a home subscriber server (HSS) or other componentstypically associated with the wireless communication service. In thisregard, for example, a user equipment (UE) can discover services andservice providers based at least in part on messages broadcast byeNodeBs (eNB) offering the services, and can perform network selectionto communicate with the eNBs to receive the service, though the servicemay not be provided by a typical mobile network operator (MNO)associated with the eNBs. For example, an eNB may advertise LTE hotspotservices provided by an owner of a related network (e.g., as opposed toan MNO), as described further herein. Credentialing for the UE can bemanaged by an authentication, authorization, and accounting (AAA) serverpresent in the wireless network.

In addition, a UE can determine whether and/or which credentials areneeded to communicate with the eNB to receive the service, and canprovide the appropriate credentials based on performing the networkselection. For example, credentials can relate parameters managed by anetwork to control access to the network for one or more UEs. Forexample, the credentials can be assigned to or specified by the UE. Inone example, credentials can include an identifier of the UE (e.g.,international mobile subscriber identity (IMSI), security root key (Ki)or other USIM credentials), username/password pairs, and/or similarcredentials that present a UE with a challenge to access the network.Credentials can also be referred to herein as a set of credentials.Moreover, for example, credentials for the service can be provisioned tothe UE by the eNB or other network component in certain cases to allowthe UE to use the service (e.g., after paying for the service,fulfilling some other requirement to use the service, etc.). Thus, theUE can provide received or otherwise specified credentials to the AAAserver via the eNB to receive the related services. This can be usefulto provide a hotspot for long term evolution (LTE) or other wirelesscommunication service to allow UEs to utilize LTE in communicating overa network providing the hotspot by accessing the network based on thecredentials controlled by the network rather than MNO authentication. Inanother example, this can be useful to provide wireless communicationservice offload such that the network provides LTE access to subscribersof a particular mobile network operator (MNO) to extend the service areaof the MNO in a different frequency spectrum such that the LTE accesscan be managed by a third party. These examples may utilize anunlicensed frequency spectrum to communicate with the UEs. In thisregard, LTE access service can be provided to UEs by networks that maybe managed by entities that may not include MNOs related to a homenetwork of the UEs by allowing the service identification information(e.g., a service identifier of LTE) to be decoupled from the networkidentification information.

As used in this application, the terms “component,” “module,” “system”and the like are intended to include a computer-related entity, such asbut not limited to hardware, firmware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a computing device and the computing device can be a component. Oneor more components can reside within a process and/or thread ofexecution and a component can be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components can communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets, such as data from one component interactingwith another component in a local system, distributed system, and/oracross a network such as the Internet with other systems by way of thesignal.

Furthermore, various aspects are described herein in connection with aterminal, which can be a wired terminal or a wireless terminal. Aterminal can also be called a system, device, subscriber unit,subscriber station, mobile station, mobile, mobile device, remotestation, remote terminal, access terminal, user terminal, terminal,communication device, user agent, user device, user equipment, or userequipment device. A wireless terminal can be a cellular telephone, asatellite phone, a cordless telephone, a Session Initiation Protocol(SIP) phone, a wireless local loop (WLL) station, a personal digitalassistant (PDA), a handheld device having wireless connectioncapability, a computing device, or other processing devices connected toa wireless modem. Moreover, various aspects are described herein inconnection with a base station. A base station can be utilized forcommunicating with wireless terminal(s) and can also be referred to asan access point, access node, a Node B, evolved Node B (eNB), or someother terminology.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

The techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA system may implement a radio technology such as EvolvedUTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are partof Universal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) is a release of UMTS that uses E-UTRA, which employsOFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTEand GSM are described in documents from an organization named “3rdGeneration Partnership Project” (3GPP). Additionally, cdma2000 and UMBare described in documents from an organization named “3rd GenerationPartnership Project 2” (3GPP2). Further, such wireless communicationsystems may additionally include peer-to-peer (e.g., mobile-to-mobile)ad hoc network systems often using unpaired unlicensed spectrums, 802.xxwireless LAN (WLAN), BLUETOOTH and any other short- or long-range,wireless communication techniques.

Various aspects or features will be presented in terms of systems thatcan include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems can includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches can also be used.

Referring to FIG. 1, a wireless communication system 100 is illustratedthat facilitates providing wireless access to network services. System100 includes a wireless communication service hotspot 102, which canprovide a cell to receive wireless communications from one or more UEsto provide access to a backend service provider network 104 (e.g., viaone or more other co-located or remotely located network nodes). In thisexample, the components shown in the wireless communication servicehotspot 102 typically may communicate to provide access to a specificmobile network operator using the wireless communication service, suchas LTE, GSM, etc. In this example, a UE 106 communicates with an eNB 108portion of the wireless communication service hotspot 102 that providesthe cell, such to access a serving gateway (SGW)/packet data network(PDN) gateway (PGW) 110 and/or a mobility management entity 112, whichmay also be included in the hotspot 102. In one example, where the eNB108 communicates using an LTE radio access technology, the wirelesscommunication service hotspot 102 may be referred to as an LTE hotspot.This configuration can also be referred to as LTE unlicensed for WLAN(LTE-U-W) deployment.

The wireless communication service hotspot 102 may be operated byvarious operators (e.g., a residential network operator, an enterprisenetwork operator, a cable network operator, etc.) to provide LTE radionetwork access to the service provider network 104. In this regard, thewireless communication service hotspot 102 may not be associated with aMNO and thus may not be identifiable by a PLMN ID (e.g., where thenetwork operator does not have an associated mobile network code (MNC)that forms part of the PLMN ID). Accordingly, as described furtherherein, network identification information and service identificationinformation can be decoupled at the wireless communication servicehotspot 102 such to allow the UE 106 to separately identify the networkoperator and/or service information of the wireless communicationservice hotspot 102. Accordingly, for example, the UE 106 may include anetwork/service connecting component 306, as described further herein,to request information regarding network services, supportedsubscription providers, credentials, etc. In addition, for example, eNB108 may include a network/service decoupling component 308, as describedfurther herein, to provide network identification information andservice identification information to one or more UEs. As described, forexample, the network identification information may include one or moreidentifiers of a network providing the services, and the serviceidentification information may include supported subscription providers,information for obtaining credentials, etc. Moreover, for example,SGW/PGW 110 may include a communication managing component 818 that maylimit external communications to one or more components of the serviceprovider network 104 while obtaining credentials for the UE 106.

UE 106 can include any type of mobile device, such as, but not limitedto, a smartphone, cellular telephone, mobile phone, laptop computer,tablet computer, or other portable networked device that can be astandalone device, tethered to another device (e.g., a modem connectedto a computer), and/or the like. In addition, UE 106 may also bereferred to by those skilled in the art as a mobile station, asubscriber station, a mobile unit, a subscriber unit, a wireless unit, aremote unit, a mobile device, a mobile communications device, a wirelessdevice, a wireless communications device, a remote device, a mobilesubscriber station, an access terminal, a mobile terminal, a wirelessterminal, a remote terminal, a handset, a terminal, a user agent, amobile client, a client, or some other suitable terminology. In general,UE 106 may be small and light enough to be considered portable and maybe configured to communicate wirelessly via an over-the-aircommunication link using one or more OTA communication protocolsdescribed herein. Additionally, in some examples, UE 106 may beconfigured to facilitate communication on multiple separate networks viamultiple separate subscriptions, multiple radio links, and/or the like.

eNB 108 may include an access point, such as a macro cell access point,a small cell access point, and/or the like. As used herein, the term“small cell” may refer to an access point or to a corresponding coveragearea of the access point, where the access point in this case has arelatively low transmit power or relatively small coverage as comparedto, for example, the transmit power or coverage area of a macro networkaccess point or macro cell. For instance, a macro cell may cover arelatively large geographic area, such as, but not limited to, severalkilometers in radius. In contrast, a small cell may cover a relativelysmall geographic area, such as, but not limited to, a home, a building,or a floor of a building. As such, a small cell may include, but is notlimited to, an apparatus such as a BS, an access point, a femto node, afemtocell, a pico node, a micro node, a Node B, eNB, home Node B (HNB)or home evolved Node B (HeNB). Therefore, the term “small cell,” as usedherein, refers to a relatively low transmit power and/or a relativelysmall coverage area cell as compared to a macro cell.

In typical LTE deployments, for example, the MME 112 provides the UE 106with bearer setup procedures, access to SGW/PGW 110 and other core MNOnetwork components (e.g., an HSS), etc., and SGW/PGW 110 provides the UE106 with access to an Internet connection and/or other external nodes.In the depicted example, however, SGW/PGW 110 and MME 112 provide the UE106 with access to service provider (SP) data network 120. It is to beappreciated, in this regard, that the MME 112 can setup a bearer for UE106 to communicate via eNB 108 to access components of the serviceprovider network 104 via SP data network 120. This can include settingup a radio bearer between UE 106 and eNB 108 as well as a data bearerbetween eNB 108 and SGW/PGW 110 and/or additional components of network104. In addition, the user and control plane communications may becollapsed for communicating with certain elements in the network 104.Moreover, for example, security can be modified such to use extensibleauthentication protocol (EAP) or similar security mechanisms over thenon-access stratum (NAS) layer between UE 106 and mobility managemententity (MME) 112, as described further herein.

Network 104 further includes an AAA server 122 for establishing andverifying credentials of UE 106 for accessing the network 104. SP datanetwork 120 can also provide access to Internet 124. Additional serversmay optionally be included in the network 104 as well, such as a policyserver 126 that can define one or more access policies for a set ofcredentials, a subscription remediation server 128 that can resolvesubscription errors and/or timeouts, and/or an online sign-up (OSU)server 130 for managing subscription credentials for accessing network104. OSU server 130 can communicate with certificate authority 132 toobtain one or more certificates for managing subscription-based accessto network 104. In an example, network 104 can also include a router(not shown) to facilitate WiFi or other wireless access thereto.

In an example, eNB 108 can advertise network services that arediscoverable by UE 106 by broadcasting one or more messages indicatingavailable services. The UE 106 can detect the broadcast message from theeNB 108, can establish a connection with the eNB 108 (e.g., based oninformation in the broadcast message), and can query the eNB 108 forservices available and/or related information, such as subscriptionprovider information, credential information or other information tofacilitate establishing one or more of the services with the eNB 108.eNB 108 can return the queried information, and UE 106 can establish aservice with the eNB 108 based at least in part on the serviceavailable, related information, etc. For example, the service may relateto one or more services including accessing network resources viaservice provider network 104.

Accordingly, for example, eNB 108 may indicate subscription providerinformation for accessing service provider network 104, and UE 106 canprovide the appropriate credentials to the eNB 108 for one or moreindicated subscription providers. For example, eNB 108 may request ausername/password, personal identification number (PIN), etc. from theUE 106, and the UE 106 can provide the appropriate username/password,PIN, etc. for the service (e.g., based on credentials input via aninterface of the UE 106, based on credentials stored at the UE 106 for agiven subscription provider or otherwise indicated to the UE 106 by theeNB 108, etc.). In another example (e.g., where the UE 106 does not havecredentials for the indicated subscription provider), the eNB 108 canprovide a sign-up page requesting registration information forregistration of a username/password, requesting payment or acceptance ofterms, requesting a certificate, etc. by the UE 106. In this example,when registration information is provided, the eNB 108 can communicatethe registration information to the OSU server 130, which can approvethe registration information and obtain credentials and/or acertificate, from certificate authority 132, for the UE 106. OSU server130 can update the AAA server 122 with the credentials for subsequentauthentication of the UE 106.

In this regard, UE 106 can request attachment from MME 112 (e.g., usingEAP), via eNB 108, by specifying the credentials received from theservice provider network 104. In one example, UE 106 can indicate anauthentication type as well. MME 112 can provide the credentials (and/orrequested authentication type) to AAA server 122. The AAA server 122 canauthenticate the UE 106 to access one or more services on serviceprovider network 104. It is to be appreciated that verifying credentialsby the AAA server 122 can additionally include verifying the credentialsfor a particular usage or service indicated by eNB 108 for UE 106 basedon one or more policies for the UE 106 in policy server 126. In anycase, once the UE 106 is authenticated, MME 112 can trigger a PDNestablishment procedure to the service provider network 104 via SGW/PGW110 to facilitate providing the requested service to UE 106 over anauthenticated connection. For example, this can include MME 112 settingup one or more bearers between the eNB 108 and SGW/PGW 110 for accessingthe network 104, and/or an associated radio bearer between UE 106 andeNB 108.

Moreover, though shown as separate devices, it is to be appreciated thatthe different devices may be collapsed into a single actual device thatperforms the specific functions in some deployments. For example, in anenterprise network, the MME 112 and AAA server 122 functions can beprovided in a single entity. In another example, in a residentialnetwork for instance, eNB 108, SGW/PGW, MME 112, and AAA server 122(and/or OSU server 130) can be combined in a single device that can beconnected to a home network such that the SGW/PGW functionality providesUE 106 with access to Internet 124 via the home network. In otherdeployments, it is to be appreciated that some of the components shownin the hotspot 102 can be included in the network 104 along with agateway function. For instance, in an example deployment, SGW/PGW 110and MME 112 can be provided in the network 104, along with an HNBgateway that communicates with various eNBs 108 in various hotspotdeployments 102 to provide access to SGW/PGW 110 and/or MME 112.

Referring to FIG. 2, a wireless communication system 200 is illustratedthat facilitates providing wireless access to network services. System200 includes a radio access network (RAN) 202 that provides LTE offload,or offload for other wireless communication services (e.g., UMTS), wherethe RAN 202 communicates with a visiting public land mobile network(PLMN) evolved packet core (EPC) to allow access to Internet 124. System200 also depicts a home PLMN (HPLMN) EPC 206 that manages credentialsfor certain UEs. RAN 202 comprises an eNB 108 and a local gateway (LGW)210 that facilitate communicating with components of the visiting PLMN(VPLMN) EPC 204 and/or Internet 124. VPLMN EPC 204 is referred to as thevisiting PLMN because it is not the HPLMN for UE 106, in this example.VPLMN EPC 204 comprises a SGW/PGW 110 (depicted as separate devices) andan MME 112. HPLMN EPC 206 includes an AAA server 212, which may bedifferent than AAA server 122 of network 104 (FIG. 1) as this AAA server212 manages AAA functions of the HPLMN EPC, and an HSS 214 for storingsubscription information of certain UEs, such as UE 106. Serviceidentification information can be decoupled from network identificationinformation at the RAN 202 such to allow the UE 106 to separatelyidentify the network operator of (corresponding to the networkidentification information) and/or service (corresponding to the serviceidentification information) provided by the RAN 202. Accordingly, forexample, the UE 106 may include a network/service connecting component306, as described further herein, to request information regardingnetwork services, supported subscription providers, credentials, etc. Inaddition, for example, eNB 108 may include a network/service decouplingcomponent 308, as described further herein, to provide networkidentification and service identification information to one or moreUEs, where the service identification information may include supportedsubscription providers, information for obtaining credentials, etc.Moreover, for example, SGW 110 (and/or PGW 110) may include acommunication managing component 818 that may limit externalcommunications to one or more components of the service provider network104 while obtaining credentials for the UE 106.

In this example, the VPLMN EPC 204 and HPLMN EPC 206 can function as atypical mobile network to provide UEs related to the HSS 214 of theHPLMN EPC 206 with access to Internet 124 or other network resourcesbased on the VPLMN EPC 204 verifying subscription information of the UE106 with HPLMN EPC 206. The RAN 202 can be deployed at a third partythat connects to the VPLMN EPC 204 via Internet 124 (e.g., using LGW210). In this example, eNB 108 operates in an unlicensed frequencyspectrum to communicate with UE 106, and provides UE 106 with access toInternet 124 by traversing the VPLMN EPC 204 to which RAN 202 connects,and HPLMN EPC 206 related to the UE 106. Thus, for example, UE 106 canuse universal subscriber identity module (USIM) credentials to accessRAN 202, where RAN 202 verifies the credentials by accessing HPLMN EPC204. For example, UE 106 can determine to use the USIM credentials basedat least in part on identifying a subscription provider corresponding tothe USIM credentials in one or more supported subscription providersindicated by the eNB 108, as described further herein. In this regard,the UE 106 can utilize Internet 124 by offloading to RAN 202 where RAN202 is able to authenticate the UE 106 via HPLMN EPC 206.

Turning now to FIGS. 3-7, aspects of the present apparatus and methodare depicted with reference to one or more components and one or moremethods that may perform the actions or functions described herein.Although the operations described below in FIGS. 4, 5, and 7 arepresented in a particular order and/or as being performed by an examplecomponent, it should be understood that the ordering of the actions andthe components performing the actions may be varied, depending on theimplementation. Moreover, it should be understood that the followingactions or functions may be performed by a specially-programmedprocessor, a processor executing specially-programmed software orcomputer-readable media, or by any other combination of a hardwarecomponent and/or a software component capable of performing thedescribed actions or functions.

FIG. 3 depicts a system 300 for determining information for performingnetwork selection in a wireless network. System 300 includes a UE 106that communicates with a network entity 304 to inquire about networkservices and/or to utilize one or more network services, as describedherein. Network entity 304, for example, may include an eNB, such as eNB108, an MME, such as MME 112, and/or substantially any network componentthat can communicate information to UE 106.

UE 106 may include a network/service connecting component 306 fordetermining network identification information and/or serviceidentification information related to network entity 304. For example,network/service connecting component 306 may include an identifierdetermining component 310 for determining network identificationinformation associated with a network entity, a connection establishingcomponent 312 for establishing a connection with the network entitybased at least in part on the network identification information, and aservice querying component 314 for querying the network entity for aserving provider related thereto, as described herein.

Network entity 304 may include a network/service decoupling component308 for separately indicating network identification information and/orrelated service identification information. Network/service decouplingcomponent 308 may include an identifier broadcasting component 316 forbroadcasting network identification information, a connectionestablishing component 318 for facilitating connection establishmentwith one or more UEs, and a service provisioning component 320 forprovisioning service information (e.g., an indication of a serviceprovider) to the one or more UEs.

FIG. 4 depicts an example method 400 for querying an eNB for serviceinformation. FIG. 5 illustrates an example method 500 for providingservice information to a UE. Method 400 of FIG. 4 includes, at Block402, determining a network identifier in a broadcast message receivedfrom a network entity. Identifier determining component 310 candetermine the network identifier (or other network identificationinformation) in the broadcast message received from the network entity(e.g., network entity 304, which may include an eNB, MME, etc.). Method500 of FIG. 5 includes, at Block 502, broadcasting a message including anetwork identifier. Identifier broadcasting component 316 can broadcastmessage including the network identifier. For example, identifierbroadcasting component 316 can broadcast the message over the air suchthat the message can be received by the UE 106 when within a range ofnetwork entity 304. Moreover, for example, the message can be abroadcast message such that the UE 106 need not connect to the networkentity 304 to establish dedicated resources before receiving themessage. The network identifier, for example, can indicate an owner ofthe service provider network (e.g., network 104 in FIG. 1) to which thenetwork entity 304 relates. In an example, the broadcast message fromthe network entity 304 can also relate to a message from an MMEtransmitted via an eNB.

In an example, the network identifier can indicate a deployment model ofthe service provider network. For example, the network identifier caninclude a PLMN identifier (ID), which can indicate an LTE network typeor an LTE offload network type that may be associated with a MNO (e.g.,as shown in FIG. 2). In another example, the network identifier caninclude an access network (AN) ID that indicates a network that may notbe associated with a PLMN ID (e.g., a non-traditional MNO network suchas an LTE hotspot as shown in FIG. 1). For example, the AN ID can be anidentifier encoded into system information (e.g., SIB1, or as a newidentifier in a new information element (IE), or a reused existing IE,such as PLMN ID using a defined value), etc., as described furtherherein. In yet another example, the network identifier can include aclosed subscriber group (CSG) identifier that can be used along withanother private network ID, a public network ID (e.g., a PLMN ID), ANID, etc., to indicate a private network accessible by UEs in the CSG,where the eNB 108 can support private and/or public networks. In thisregard, identifier determining component 310 obtains the networkidentifier from the broadcast message from the network entity 304, fromwhich a type of network deployment may be determined. It is to beappreciated that a type of the network deployment (e.g., LTE, LTEoffload, LTE hotspot, etc.) can be additionally broadcast in otherinformation from network entity 304 (e.g., system information block(SIB) or other broadcast message).

In addition, it is to be appreciated that network entity 304 canbroadcast a text based representation of the network identifier, whichthe identifier determining component 310 can receive for displaying onan interface (not shown) of the UE 106. For example, the text basedrepresentation can include a HNB name or other property of the networkentity 304 for identification thereof, and may be broadcasted inaddition to a CSG identifier for advertising a CSG network. An exampleof network identifiers that the identifier broadcasting component 316can broadcast in the message for different types of deployments andnetworks can be as follows:

Deployment type Network (public) Network (private) Operator or offloadPLMN CSG (optional) operator Combined LTE offload PLMN + AN CSG operatorand LTE HotSpot operator LTE Hotspot operator AN (optional) CSG only,e.g., residential, enterprise, stadium, cableMoreover, for example, identifier broadcasting component 316 canbroadcast multiple identifiers for a given network entity 304 toindicate multiple deployment types. In an example, identifierbroadcasting component 316 may broadcast one identifier for an LTE orLTE offload network (e.g., a PLMN ID) and another identifier for a LTEhotspot network (e.g., an AN ID) such to allow UEs to access the networkentity 304 according to one or the other network deployment types basedon subscription information.

In an example, where the PLMN ID is used, a special PLMN ID indicatingthe deployment type of the network can be used. In another example, anAN ID can be encoded in existing SIB messages broadcasted by identifierbroadcasting component 316 as part of the wireless communication service(e.g., as part of LTE) to indicate the deployment type of the network,where the SIB can include the AN ID as a new information element (IE), areuse of an existing ID (e.g., PLMN ID in SIB1), etc. In one example,where PLMN ID is encoded using binary coded decimal, some combinationsare not used, and as such, unused portions of the PLMN ID in SIB1 may beused to specify the AN ID. In yet another example, identifierbroadcasting component 316 can use a cell ID or tracking area code toindicate the AN ID (e.g., where PLMN ID is not present).

In addition, method 400 includes, at Block 404, establishing aconnection with a network based at least in part on the networkidentifier. Connection establishing component 312 can establish theconnection with the network (e.g., network entity 304) based at least inpart on the network identifier. For example, this can optionally includedetermining a deployment type of the network, at Block 408. As describedfurther herein, the connection may be an unauthenticated connection thatis established based on the deployment type of network. Thus, where thenetwork deployment type is an LTE offload, LTE hotspot, etc. network,connection establishing component 312 may establish the unauthenticatedconnection to determine one or more subscriptions supported by thenetwork, AAA server information, etc. to determine credentials forestablishing an authenticated connection with the network (e.g., via anassociated AAA server), and/or the like. Similarly, method 500 includes,at Block 504, establishing a connection with one or more UEs. Connectionestablishing component 318 can facilitate establishing the connection(e.g., whether authenticated or unauthenticated) with the one or moreUEs (e.g., UE 106).

In another example, connection establishing component 312 can determineto establish the connection if the UE 106 is a member of a CSGadvertised by network entity 304. Thus, it is to be appreciated that theconnection establishing component 318 can verify whether the UE 106 is amember of a broadcasted CSG before establishing the connectiontherewith, in one example.

In an example, the connection established between connectionestablishing components 312 and 318 may be an unauthenticated connectionover a radio resource control (RRC) layer or other layer 3 (e.g., wherenetwork entity 304 is an eNB), over a NAS layer (e.g., where networkentity 304 is an MME), and/or the like. The purpose of the connectioncan be to obtain additional information regarding services providedand/or subscriptions supported by the network entity 304. Thus, theconnection can offer limited services in this regard. Thus, for example,method 400 includes, at Block 406, querying, using the connection, thenetwork for information related to establishing services at the network.Service querying component 314 can query, using the connection, thenetwork (e.g., network entity 304) for the information related toestablishing services at the network. This can include informationregarding the services (e.g., an identification of the services),subscriptions supported (e.g., a type of credentials for accessing theservices), and/or the like in a service query. In an example, servicequerying component 314 may formulate the query based at least in part ondetermining that such querying is supported by the network entity 304,which the network entity 304 may indicate in a broadcast message (e.g.,SIB) or other signaling to the UE 106. Method 500 includes, at Block506, providing service information to the one or more UEs. Serviceprovisioning component 320 can provide the service information to theone or more UEs (e.g., UE 106). The service information may relate toservices offered, subscription identifiers (or identifiers ofsubscription providers) supported, etc. to the UE 106, which can bebased on a request received from the UE 106 or otherwise based onestablishing the connection with the UE 106.

Thus, for example, a service discovery protocol (SDP) can be defined forcommunicating service and/or subscription information between the UE 106and network entity 304. For instance, the network entity 304 isconfigured with one or more service providers and/or MNOs that provideaccess to the service provider network (e.g., network 104). Thus,service provisioning component 320 can provide information to the UE 106regarding accessing the service provider network via the one or moresubscription providers, such as subscription provider identificationinformation (e.g., name, an icon, etc.), type of authentication used,AAA server information, availability of online signup or OSU serverinformation, etc. based on a query received from service queryingcomponent 314. In one example, service provisioning component 320 canprovide the information to the UE 106 (e.g., which can be received byservice querying component 314) based at least in part on performing adomain name system (DNS) lookup to determine at least some of theinformation (e.g., AAA server information).

As described, SDP can be run over an RRC or NAS connection between UE106 and network entity 304. When run over RRC, for example, connectionestablishing component 312 can establish the RRC connection via an RRCmessage with network entity 304, where the RRC message can use a causecode to indicate an SDP query (e.g., based on an indication from servicequerying component 314), in which case connection establishing component318 can respond to the connection request with the SDP information(e.g., obtained from service provisioning component 320), whichconnection establishing component 312 can provide to service queryingcomponent 314. In another example, connection establishing component 312can request the SDP information (e.g., based on an indication fromservice querying component 314) by using a newly defined RRC messagethat requests the SDP information, but may not actually establish an RRCconnection with the network entity 304. In this example, connectionestablishing component 318 responds with a newly defined RRC messageincluding the queried SDP information (e.g., received from serviceprovisioning component 320) without establishing the connection. Forexample, the newly defined messages can be used after connectionestablishing component 312 receives a response (message 2) fromconnection establishing component 318 to an initial random accesschannel (RACH) request. The transaction can be assumed complete once thenetwork entity 304 transmits the SDP response to the UE 106.

In any case, whether SDP is performed by RRC or NAS, it may be run onceper network identifier observed by UE 106 to determine if the UE 106 hasa valid subscription to access the related service provider network, orto provision a new subscription at a new/unrecognized service providernetwork. In addition, in an example, identifier broadcasting component316 may broadcast service and/or subscription information (e.g.,subscription identifiers) in the broadcast message with the networkidentifier (or another broadcast message) such that a connection neednot be established with network entity 304 to receive the service and/orsubscription information. In one example, subscription identifiers sentto the UE 106 in the SDP query response or in a broadcast message canindicate which subscription(s) or subscription provider(s) are validand/or supported at the network entity 304 for accessing the serviceprovider network (e.g., and/or for accessing portions thereof accordingto one or more policies related to the subscriptions or type ofsubscriptions). In this regard, for example, the UE 106 can determinewhether it has credentials for the specific subscription provider indetermining whether to access network entity 304 to receive one or moreservices, as described further herein.

In this regard, method 400 may optionally include, at Block 410,establishing an authenticated connection with the network based at leastin part on the information. Connection establishing component 312 mayestablish the authenticated connection with the network based at leastin part on the information. Similarly, method 500 may optionallyinclude, at Block 508, establishing an authenticated connection with theone or more UEs based at least in part on the service information.Connection establishing component 318 may establish the authenticatedconnection with the one or more UEs based at least in part on theservice information. For example, the authenticated connection caninclude a connection between the UE 106 and network entity 304 that isestablished based on a set of credentials. For example, the set ofcredentials may include at least one of subscription information of theUE 106 (e.g., where network entity 304 is or communicates with an LTE,LTE offload, or similar network entity), where the subscriptioninformation can be obtained from an HPLMN of the UE, credentialsspecified by the UE 106 (e.g., where network entity 304 is orcommunicates with an LTE hotspot that requests credentials and/or anonline sign-up, as described herein), etc.

For example, establishing the authenticated connection with the networkat Block 410 may optionally include, at Block 412, determining a set ofcredentials for the authenticated connection based on receivinginformation of one or more subscription providers. Connectionestablishing component 312 can determine the set of credentials for theauthenticated connection based on receiving information of one or moresubscription providers. For example, the information received at Block406 may include the information of the one or more subscriptionproviders, and may include an identifier of the subscription provider.This can enable the connection establishing component 312 to determinecredentials associated with the subscription provider for attempting toestablish the authenticated connection and/or a type of subscription orconnection request to utilize.

As described, connection establishing component 312 may determine thecredentials for the subscription provider based on a list of credentialsstored for a plurality of subscription providers, which may includeusername/password or PIN values, security keys, etc. and/or may bestored by the connection establishing component 312 or other componentof the UE 106. In this example, connection establishing component 312may determine a deployment type of the network or subscription asrelated to LTE hotspot, and/or otherwise that the credentials expectedare non-USIM credentials that can be validated by an AAA server that maynot be part of an LTE EPC. In another example, connection establishingcomponent 312 may determine the credentials for the subscriptionprovider based on subscription information of the UE 106 (e.g., IMSI,security root key (Ki) or other USIM credentials), etc. For example,connection establishing component 312 may determine a type of thenetwork or subscription as related to LTE or LTE offload, and/orotherwise that the credentials expected are USIM credentials that can bevalidated by an AAA server at an HPLMN of the UE 106. In another example(e.g., where connection establishing component 312 cannot locatecredentials for the subscription), connection establishing component 312may utilize an interface of the UE 106 to prompt for entry ofcredentials, which may be subsequently utilized in attempting toestablish the authenticated connection. For example, connectionestablishing component 312 may display at least a portion of the relatedsubscription or service information (e.g., the icon) using the interfaceof the UE 106.

Establishing the authenticated connection with the network at Block 410may also optionally include, at Block 414, establishing an RRC layerconnection with at least one of the one or more subscription providersbased at least in part on the set of credentials. Connectionestablishing component 312 can establish the RRC layer connection withat least one of the one or more subscription providers based at least inpart on the set of credentials. As described, the network may supportmultiple different types of subscriptions, and the connectionestablishing component 312 may select one or more of the subscriptionsfor which it has credentials (e.g., which may be stored in a list ofcredentials at the connection establishing component 312 or othercomponent of UE 106). In one example, as described, determining the setof credentials at Block 412 may include connection establishingcomponent 312 specifying credentials in signing-up for the subscriptionwith the network, and thus establishing the RRC layer connection atBlock 414 may be accomplished using the specified credentials. This mayinclude generating a username/password, PIN, etc. combination using aninterface of the UE 106, accepting terms and conditions specified forthe network entity 304, etc.

In a specific example, network entity 304 may broadcast the networkidentifier (or other network identification information) via identifierbroadcasting component 316 in an extended or adapted LTE or LTE Advancedin unlicensed spectrum, and identifier determining component 310 canobtain the identifier as broadcasted by network entity 304. For LTEhotspot networks, for example, non-USIM credentials may be used forauthenticating UE 106, in which case the credentials are not associatedwith a PLMN ID or IMSI of the UE 106. In this regard, identifierbroadcasting component 316 can broadcast a special PLMN ID (e.g., allzeros or another defined PLMN ID) for indicating LTE hotspotfunctionality (and/or can use a cell ID or tracking area code as an ANID, as described). In addition, as described, identifier broadcastingcomponent 316 may broadcast a CSG identifier as well to indicate privatenetwork access and/or to specify the AN ID. For example, the identifierbroadcasting component 316 may utilize the CSG ID to indicate the AN IDwhere distinguishing between CSG and non-CSG cells is not needed.

In any case, identifier determining component 310 can receive theinformation and can allow connection establishing component 312 toselect whether to establish connection with the network entity 304 as anLTE hotspot based on the information. For example, connectionestablishing component 312 may determine whether the information is atleast partially within a configuration of networks from which to requestaccess, where the connection establishing component 312 may store orotherwise access configurations of networks from which to requestaccess. This configuration of networks may include a whitelist of CSGcells from which to request access, a blacklist of CSG cells from whichto not request access, a preferred roaming list of PLMN IDs of networks,a list of AN IDs or other network identification information preferredfor requesting access (e.g., as selected and/or specified using aninterface of the UE 106), etc. In addition, connection establishingcomponent 312 can determine the credentials for establishing theconnection based on the deployment type of network and/or theconfiguration within which the network is located (e.g., CSG whitelist,preferred roaming list, AN list, etc.), as described above, and mayaccordingly attempt to establish the authenticated connection with thenetwork. For an LTE hotspot subscription, for example, connectionestablishing component 312 can determine a username/passwordcombination, PIN, an online sign-up mechanism, etc. as credentials foraccessing the network, and may specify the credentials in attempting toestablish the authenticated connection with the network.

In another example, network entity 304 can broadcast a networkidentifier (or other network identification information) to indicate LTEor LTE offload network, which may include indicating the PLMN ID of therelated MNO in system information (e.g., SIB1). In this example,identifier determining component 310 can obtain the network identifier(or other network identification information), and connectionestablishing component 312 can determine the network entity 304 relatesto an MNO based on the PLMN ID. Connection establishing component 312can accordingly perform a connection procedure with the connectionestablishing component 318 as defined for the wireless communicationservice. This may include establishing a connection to determinesupported subscription providers or may otherwise include establishingan authenticated connection using subscription information of the UE 106(e.g., in LTE based on an IMSI, security root key, etc.). In thisexample, UE 106 may use the network entity 304 according to the wirelesscommunication service, and may not query for additional providedservices. It is to be appreciated that other PLMN IDs can be defined toindicate LTE offload for a given MNO, and thus the UE 106 connects tothe network entity 304 as if it is connecting to the MNO normally uponencountering one of the defined PLMN IDs.

In one example, for LTE offload subscriptions indicated by networkentity 304, connection establishing component 312 can utilize adifferent network selection mechanism than that used in selecting amongLTE subscriptions. For example, connection establishing component 312may use mechanisms similar to access network discovery and selectionfunction (ANDSF) in WLAN and/or preferred service provider list (PSPL)rules to discover and rank or select LTE offload subscriptionsdiscovered for one or more networks. In an example, the PSPL rules canspecify certain locations of the UE 106 and/or times during whichdifferent subscriptions may be ranked or otherwise preferred over othersubscriptions (e.g., to distribute usage in peak locations/hours). Inany case, connection establishing component 312 can consider receivedsubscription information for one or more networks against a preferredlist of subscriptions to determine one or more subscriptions over whichto establish an authenticated connection, as described.

FIG. 6 illustrates an example system 600 depicting message flow betweena UE 106, eNB 108, and MME 112 in accordance with aspects described withrespect to FIGS. 3-5 above. At 602, eNB 108 can broadcast SIBs that mayinclude a network identifier (e.g., in a PLMN ID or other newly definedor reused IE, a CSG identifier if applicable, etc.), which the UE 106can receive to determine a deployment type of the network. Based atleast in part on the network identifier, the UE 106 detects a LTE-U-Wdeployment, and that additional information regarding services offered,subscriptions accepted, etc., can be obtained to access the network at604. In this regard, UE 106 establishes an RRC connection with the eNB108 at 606. The RRC connection at 606 may optionally indicate an SDPquery cause code. eNB 108 accordingly allows UE 106 to establish anunauthenticated connection to obtain information regarding networkservices. In one example, as described, eNB 108 may obtain theinformation regarding network service, and return the information to UE106 without the UE 106 communicating with MME 112 over NAS. In anotherexample, however, UE 106 can optionally send an SDP query over NAS(e.g., as a NAS message) using the unauthenticated connection at 608including a request for information for service discovery to MME 112 todetermine network authentication types, OSU provider information, etc.supported at the network. In one alternative, the SDP signaling istransported over generic NAS transport, an example of which can includethe generic NAS transport of third generation partnership (3GPP)technical specification (TS) 24.301. For example, a new type of GenericNAS transport “SDP” may be defined for the receiving NAS layer to beable to provide the receiving message to the correct sublayer(SDP/Service Discovery). Alternatively, a new NAS SDP request/responsepair of messages may be used to request/receive the SDP informationbetween the UE 106 and MME 112. The MME 112 returns a SDP response at610, which may include the Network Authentication Type and OSU ProvidersList elements to UE 106, as described. The UE 106 may optionallyrequest/receive additional SDP information at 612, such as an OSUProvider Icon of the desired size in pixels in order to display theinformation to the user for provider selection, etc. In addition, asdescribed, the UE 106 can use the retrieved SDP information to determinea subscription for establishing an authenticated connection with the MME112 (or eNB 108), to display at least a portion of the SDP informationon an interface to allow selection of the subscription, etc.

FIG. 7 illustrates an example method 700 for establishing anauthenticated connection with a network entity based on determinedsubscription information for the network entity. Method 700 includes, atBlock 702, determining one or more network identifiers associated with anetwork entity. Identifier determining component 310 can determine theone or more network identifiers (or other network identificationinformation) associated with the network entity (e.g., network entity304). The one or more network identifiers may include a PLMN ID or otherpublic network ID, AN ID, CSG ID or other private network ID, etc. Inone example, identifier determining component 310 may receive anindication of the network identifier (or other network identificationinformation) from the network entity 304, which may include receivingthe indication of the network identifier in system information (e.g., aSIB) from the network entity 304.

Method 700 further includes, at Block 704, determining one or moresubscription providers associated with the one or more networkidentifiers. Connection establishing component 312 can determine the oneor more subscription providers associated with the one or more networkidentifiers. In one example, connection establishing component 312 canreceive the one or more subscription providers in configurationinformation related to the network entity 304, which may be provisionedto the UE 106 by the network entity 304 or other nodes of the wirelessnetwork (e.g., as received by service querying component 314), stored ina memory by the UE 106 (e.g., in a USIM or other persistent,non-persistent, or semi-persistent memory, etc.), and/or the like. Inone example, as described, determining the one or more subscriptionproviders at Block 704 may optionally include, at Block 706, queryingthe network entity for information regarding the one or moresubscription providers. For example, service querying component 314 mayquery the network entity 304 (e.g., using a RRC or NAS query dependingon whether the network entity 304 is an eNB or MME, as described) forinformation regarding the one or more subscription providers at least inpart by performing an SDP query to the network entity 304 or othernetwork entities, and receiving the information in response thereto. Forexample, the service querying component 314 may perform the SDP queryperiodically, based on detecting occurrence of one or more events, etc.

Method 700 also includes, at Block 708, determining a set of credentialsfor establishing an authenticated connection with the network entitybased on determining the one or more subscription providers. Connectionestablishing component 312 can determine the set of credentials forestablishing the authenticated connection with the network entity basedon determining the one or more subscription providers. As described, forexample, connection establishing component 312 may determine the set ofcredentials based at least in part on one or more lists of subscriptionsand associated credentials stored by the UE 106, by determiningcredentials specified in an online sign-up with the network entity 304,etc.

Method 700 includes, at Block 710, establishing an authenticatedconnection with the network entity using one or more of the subscriptionproviders based at least in part on the set of credentials. Connectionestablishing component 312 can establish, or at least attempt toestablish, the authenticated connection with the network entity usingone or more of the subscription providers and based at least in part onthe set of credentials. Accordingly, for example, connectionestablishing component 312 may transmit a message to network entity 304to establish the connection, and may include the set of credentialsspecific to the associated subscription. Network entity 304 mayaccordingly verify the credentials and establish or deny theauthenticated connection with the UE 106.

Turning now to FIGS. 8-11, additional aspects of the present apparatusand method are depicted with reference to one or more components and oneor more methods that may perform the actions or functions describedherein. Although the operations described below in FIGS. 9-11 arepresented in a particular order and/or as being performed by an examplecomponent, it should be understood that the ordering of the actions andthe components performing the actions may be varied, depending on theimplementation. Moreover, it should be understood that the followingactions or functions may be performed by a specially-programmedprocessor, a processor executing specially-programmed software orcomputer-readable media, or by any other combination of a hardwarecomponent and/or a software component capable of performing thedescribed actions or functions.

FIG. 8 depicts a system 800 for provisioning credentials for accessing awireless network. System 800 includes a UE 106 that communicates with anetwork entity 304 to request credentials for accessing networkservices, as described herein. Network entity 304 can communicate withone or more network components to obtain credentials for the UE 106,such as a SGW/PGW 110 and/or a credential provisioning server 802 (e.g.,via the SGW/PGW 110).

UE 106 may include a network/service connecting component 306, asdescribed, for determining network identification information and/orservice identification information related to network entity 304. Forexample, network/service connecting component 306 may include aconnection establishing component 312 for establishing a connection withthe network entity based at least in part on the network identificationinformation, a service querying component 314 for querying the networkentity for a serving provider related thereto, as described herein, anda credential requesting component 810 for requesting credentials (e.g.,from a provisioning server) for establishing the connection. It is to beappreciated that the network/service connecting component 306 mayinclude additional components, which may be omitted from this Figure forease of explanation.

Network entity 304 may include a network/service decoupling component308 for separately signaling network identification information and/orrelated service identification information, as described.Network/service decoupling component 308 may include a connectionestablishing component 318 for facilitating connection establishmentwith one or more UEs, a service provisioning component 320 forprovisioning service information (e.g., an indication of a serviceprovider) to the one or more UEs, a gateway communicating component 812for communicating with one or more gateway nodes to access a credentialprovisioning server, and/or an optional bearer activating component 814for activating one or more bearers for the UE based on establishing anauthenticated connection for the UE. It is to be appreciated that thenetwork/service decoupling component 308 may include additionalcomponents, which may be omitted from this Figure for ease ofexplanation.

SGW/PGW 110 may include a network communicating component 816 forcommunicating with one or more network nodes, and a communicationmanaging component 818 for limiting access for communicating with theone or more network nodes.

FIG. 9 depicts an example method 900 for requesting credentials foraccessing network services. FIG. 10 illustrates an example method 1000for communicating with a gateway to obtain credentials for a UE. FIG. 11shows an example method 1100 for communicating with a provisioningserver to obtain credentials for a UE. As described above, UE 106includes a connection establishing component 312 for establishing aconnection with network entity 304, which has connection establishingcomponent 318 for performing the connection establishment with UE 106.The connection can be established as an unauthenticated connection toallow the UE 106 to obtain information regarding network services and/orrelated subscription provider information supported by a network towhich network entity 304 relates. In this regard, service queryingcomponent 314 can query the network entity 304 for the information, andservice provisioning component 320 can communicate related informationto the UE 106.

Method 900 of FIG. 9 includes, at Block 902, determining thatcredentials have not been configured for accessing a network. Forexample, service querying component 314 (FIG. 8) can determine thatcredentials have not been configured for accessing the network. Forexample, service querying component 314 may determine that the UE 106does not have or has not received credentials to access one or more ofthe network services from network entity 304, and can seek to obtainprovisioning of credentials to access the network services. In oneexample, service querying component 314 can determine that the UE 106does not have the credentials based at least in part on identifyingservices received from the network entity 304, subscription providersassociated with network entity 304, etc., which may be received in oneor more identifiers from the network entity 304 as described, andsearching a data store or other memory at the UE 106 (or accessible bythe UE 106) for credentials related to the services, subscriptionproviders, etc. In another example, service querying component 314 candetermine that the UE 106 does not have the credentials based at leastin part on connection establishing component 312 attempting to accessthe network entity 304 to utilize the network services, and/or the like,and receiving a rejection for the attempt to access.

In any case, where credentials have not been received for accessing thenetwork, method 900 includes, at Block 904, selecting a provisioningserver supported by the network for obtaining credentials. For example,credential requesting component 810 can select the provisioning serversupported by the network for obtaining the credentials. Credentialrequesting component 810 may select the provisioning server based ondetermining information identifying the provisioning server, which canbe received by service querying component 314 in the informationregarding the network service and/or supported subscription providers.It is to be appreciated that UE 106 can additionally or alternativelystore information identifying the provisioning server in a memory. In anexample, credential requesting component 810 selects a provisioningserver related to a desired subscription provider (and/or can moregenerally select the subscription provider). This can be based on aselection received from an interface from UE 106, a default selection(e.g., based on parameters or preferences stored in UE 106), a random orpseudo-random selection, etc.

Method 900 may optionally include, at Block 906, determining that thenetwork allows for provisioning of credentials. Credential requestingcomponent 810 may determine that the network allows for provisioning ofcredentials. For example, this can be based on the credential requestingcomponent 810 identifying related subscription providers indicated inthe service information and determining that online provisioning ofcredentials (e.g., provisioning of credentials over the network) issupported for the subscription providers (e.g., based on a stored listof subscription providers), or otherwise obtaining an indication thatonline provisioning is supported (e.g., in service information,broadcasted with the network identifier, and/or the like). Thus, in anexample, selecting the provisioning server at Block 904 may be based atleast in part on determining that the network allows for provisioning ofcredentials.

Method 900 further includes, at Block 908, transmitting a request toestablish a connection with the network, wherein the request indicatesthe provisioning server. For example, credential requesting component810 can generate and transmit the request to establish the connectionwith the network, wherein the request indicates the provisioning server(e.g., and/or the related subscription provider). Connectionestablishing component 312 can attempt to establish a connection withnetwork entity 304 by transmitting the request thereto. It is to beappreciated that the network entity 304 to which the UE 106 transmitsthe request may be different from the network entity 304 from which thenetwork service information and/or supported subscription providerinformation is received, in one example. In an example, the request caninclude a NAS message, which can be an attach request or other existingNAS message, which may have a new IE indicating provisioning isexpected, a newly defined NAS message indicating provisioning is to beperformed, etc. Moreover, in an example, the request may include an IMSIor other substantially unique identifier of the UE 106. In one example,credential requesting component 810 may use an International MobileStation Equipment Identity (IMEI) in the request or otherwise whenestablishing the connection with network entity 304. Moreover, in someexamples, the request to establish the connection may identify theprovisioning server from which to obtain the credentials to access thenetwork. For example, the request may indicate an access point name(APN) that represents the provisioning server (or more generally arelated network service of the network entity 304 and/or the networkassociated therewith), a new IE indicating the provisioning server, aprovisioning server index or identifier, a type of provisioning server,a default provisioning server, etc. In any case, the network entity 304can determine the provisioning server to utilize in provisioningcredentials to the UE 106 based at least in part on the request (e.g.,by matching the provisioning server or corresponding network serviceindicated in the APN, information in the new IE, the server index oridentifier, the server type, etc. with the corresponding provisioningserver, such as credential provisioning server 802, as described furtherherein).

Method 1000 of FIG. 10 includes, at Block 1002, receiving a request toestablish a connection from a UE. Connection establishing component 318can receive the request to establish the connection from the UE (e.g.,UE 106). For example, the request may relate to the request transmittedby the UE 106 at Block 908, and thus may include an attach request orother NAS message that may also request provisioning of credentials.Thus, the request can be a request to establish a connection withnetwork entity 304 for the purposes of receiving credentials foraccessing an associated network, as described. In one example, it is tobe appreciated that the connection can include an unauthenticatedconnection that may have been established to receive the network serviceinformation and/or subscription provider information from the networkentity 304, as described. An identification of the provisioning servercan be sent from the UE 106 to the network entity 304 in the connectionrequest and/or otherwise while the connection is still open (e.g., basedon receiving the network service and/or subscription providerinformation). In any case, connection establishing component 318 candetermine that the connection request is for the purpose of provisioningcredentials. For example, connection establishing component 318 maydetermine this based on information that can be included in the request,as described above, such as an identified provisioning server (e.g.,based on an APN, a new IE, a server index or identifier that identifiesthe provisioning server), an identified type of provisioning server, anindication to use a default provisioning server, a special type of NASmessage or IE in the NAS message, that indicates provisioning is to beperformed, etc. Moreover, connection establishing component 318 canallow the connection with the UE 106, and may not enable security forthe connection such to maintain an unauthenticated connection, allowingthe unauthenticated UE 106 to obtain credentials for accessing servicesprovided by the network. In this regard, for example, connectionestablishing component 318 accepts the request and/or can indicate(e.g., to the UE 106 in a response to the request) that the connectionis temporary and/or is otherwise restricted to provisioning of thecredentials. In one example, it is to be appreciated that acceptance ofthe request as indicated by the connection establishing component 318may indicate that the connection is temporary and/or is otherwiserestricted to provisioning of the credentials.

Method 1000 includes, at Block 1004, selecting a gateway forestablishing a packet data context for the UE based at least in part onthe request. For example, network entity 304 includes the gatewaycommunicating component 812 for selecting the gateway for establishingthe packet data context for the UE based at least in part on therequest. In an example, the gateway can be a default gateway forprovisioning credentials to UEs. In another example, method 1000 mayoptionally include, at Block 1006, determining a provisioning server forrequesting provisioning of credentials based on the request, andselecting the gateway at Block 1004 may be based at least in part on thedetermined provisioning server. Connection establishing component 318may determine the provisioning server for requesting provisioning of thecredentials based on the request. For example, as described, theprovisioning server may be identified in the request (e.g., based on anAPN, an IE in the NAS message indicating the provisioning server, aserver index or identifier, a type of provisioning server, etc.). In anycase, in this example, gateway communicating component 812 may selectthe gateway based on the determined provisioning server, provisioningserver type, etc. In one example, gateway communicating component 812can store, or can otherwise access, a repository in a data store orother memory that associates provisioning servers with related gatewaysthat can provide access to the provisioning servers. In another example,where the request does not specify a provisioning server or otherwisespecifies an indication to request provisioning from a defaultprovisioning server, gateway communicating component 812 can select agateway that can access a default provisioning server. In this regard,gateway communicating component 812 can determine the appropriategateway for the indicated provisioning server (e.g., credentialprovisioning server 802), which may include SGW/PGW 110 in the depictedexample. In addition, for example, gateway communicating component 812can deactivate access to other gateways (not shown) for UE 106 torestrict access while the UE 106 is not yet authenticated.

Method 1000 also includes, at Block 1008, sending a session requestmessage to the gateway to establish the packet data context for the UE.Thus, for example, gateway communicating component 812 sends the sessionrequest message to the gateway (e.g., SGW/PGW 110) to establish thepacket data context for the UE (e.g., for accessing the provisioningserver indicated in the connection request from the UE 106). In oneexample, gateway communicating component 812 can indicate to SGW/PGW 110that the session for the UE 106 is limited to communicating with theparticular provisioning server (e.g., such that the gateway can controltraffic to the provisioning server for such purposes). When the packetdata context is established based on the create session request message(e.g., as a packet data network connection), network entity 304 cancommunicate with the SGW/PGW 110 over the packet data context in a PDNon behalf of the UE 106. As described, in one example, it is to beappreciated that the connection request from the UE 106 can insteadindicate the desired subscription provider, from which the gatewaycommunicating component 812 can determine the corresponding gatewayand/or provisioning server, and can accordingly send the session requestto the gateway.

Method 1100 of FIG. 11 includes, at Block 1102, establishing a sessionfor a UE for provisioning credentials to access a network. SGW/PGW 110can include a network communicating component 816 for establishing thesession for the UE for provisioning credentials to access the network.For example, network communicating component 816 may receive the requestfrom one or more network components, such as network entity 304, and therequest may include a session request sent by gateway communicatingcomponent 812 (e.g., at Block 1008). In one example, the request mayindicate a provisioning server, a related subscription provider, otherindication that the session is for provisioning credentials to a UE,additional specific information regarding the network service provider,and/or the like. Network communicating component 816 may grant therequest for the purposes of requesting provisioning of credentials, asdescribed herein. In one example, network communicating component 816can provide a context to the network entity 304 for requestingprovisioning of credentials for one or more UEs. Thus, for example, aspart of establishing the session, network communicating component 816may transmit a create session response to the network entity 304indicating that the request is granted. Thus, method 900 may optionallyinclude, at Block 910, establishing a session with the provisioningserver over the connection with the network. Credential requestingcomponent 810 can establish the session with the provisioning server(e.g., credential provisioning server 802) over the connection with thenetwork (e.g., network entity 304), which may be based on the sessionestablished with the network entity 304 by the network communicatingcomponent 816.

Method 1100 further includes, at Block 1104, determining specificinformation regarding a provisioning server. For example, SGW/PGW 110includes communication managing component 818 for determining thespecific information regarding the provisioning server. In one example,as described, communication managing component 818 can determine theprovisioning server, a related subscription provider, etc., from thesession request received from network entity 304. In addition, in anexample, communication managing component 818 may determine informationspecific to the UE 106 from the session request, and may use thisinformation in determining an associated provisioning server. In yetanother example, communication managing component 818 may determine adefault provisioning server, a provisioning server based on a type ofprovisioning server specified in the request, etc. Moreover, forexample, network communicating component 816 may explicitly requestspecific information of the network service provider and/or UE 106 fromnetwork entity 304 after establishing the session therewith, which mayinclude a request to a DNS server to identify the provisioning server.

Method 1100 includes, at Block 1106, limiting external access for the UEto the provisioning server. For example, communication managingcomponent 818 may limit external access for the UE (e.g., UE 106) to theprovisioning server (e.g., credential provisioning server 802). In thisregard, communication managing component 818 can allow communicationswith credential provisioning server 802 for the given session with thenetwork entity 304 that is associated with the packet data context, butcan forbid access requests for other nodes or gateways accessible bySGW/PGW 110 in the given session. In addition, method 1000 may include,at Block 1010, activating one or more data bearers for the UE based onthe request and associating the packet data context with the one or moredata bearers. Thus, for example, bearer activating component 814 canactivate the one or more data bearers for the UE (e.g., UE 106) based onthe request and can associate the packet data context with the one ormore data bearers. In an example, activating the one or more databearers may include indicating activation of the one or more databearers to the UE 106 when the packet data context is established (e.g.,based on receiving the create session response to the session requestmessage transmitted to the SGW/PGW 110 that indicates establishment ofthe packet data context). Bearer activating component 814 associates thedata bearer(s) with UE 106 such that communications from the databearer(s) (e.g., received over the packet data context) can be sent toUE 106 over one or more radio bearers with an eNB and/or informationfrom UE 106 may be sent over the packet data context.

Accordingly, for example, method 900 may optionally include, at Block912, requesting and receiving credentials over the connection.Credential requesting component 810 can request and receive thecredentials over the connection. For example, where the packet datacontext and associated bearer(s) are established for the UE 106 (whichmay be indicated in a NAS message from network entity 304, such as anattach response), credential requesting component 810 can transmit arequest for credentials to credential provisioning server 802 over theone or more bearers. For example, this request may occur over HypertextTransfer Protocol Secure (HTTPS), Open Mobile Alliance (OMA) DeviceManagement (DM), Simple Object Access Protocol (SOAP) eXtensible MarkupLanguage (XML), etc. Based on the request, for example, credentialprovisioning server 802 can obtain credentials for the UE 106. In oneexample, the credentials can be provisioned based at least in part oninformation previously provided by the UE 106 (e.g., to credentialprovisioning server 802 or other components of the network) such asregistration information (e.g., input on the UE 106), username/passwordcombination, request for a certificate, payment information, acceptanceof terms/conditions, and/or the like.

In this regard, method 1100 may include, at Block 1108, communicatingcredentials from the provisioning server to the UE over one or more databearers established for the UE. Thus, network communicating component816 can communicate the credentials from the provisioning server (e.g.,credential provisioning server 802) to the UE (e.g., UE 106) over theone or more data bearers established for the UE that may be related tothe packet data context. Gateway communicating component 812 receivesthe credentials over the one or more data bearers, and sends thecredentials to the UE 106 over the connection established via connectionestablishing component 318 (e.g., over a radio bearer for the UE 106).Credential requesting component 810 can receive the credentials from theprovisioning server over the connection with the network entity 304.Method 900 may optionally include, at Block 914, establishing anauthenticated connection with the network based at least in part on thecredentials. Thus, as described further herein, connection establishingcomponent 312 can establish the authenticated connection with thenetwork (e.g., with network entity 304) based at least in part on thecredentials.

Method 1100 can also optionally include, at Block 1110, communicatingthe credentials for the UE to one or more network components as well. Inthis example, network communicating component 816 can communicate thecredentials for the UE (e.g., UE 106) to the one or more networkcomponents. For example, the one or more network components may includean AAA server, a HSS, etc. (not shown) for updating such that the AAAserver, HSS, etc. can subsequently authenticate a connection requestfrom the UE 106.

In addition, method 1000 may optionally include, at Block 1012,releasing the one or more data bearers and/or the session with thegateway after a period of time. For example, bearer activating component814 can release the one or more data bearers and/or gatewaycommunicating component 812 can release the session with the gateway(e.g., SGW/PGW 110) after the period of time. In one example, beareractivating component 814 can deactivate the one or more bearers and/orgateway communicating component 812 can terminate the session withPGW/SGW 110 after the period of time, which can be measured from thetime of bearer activation and/or session initiation. For example, theperiod of time can represent a time after which it is determined thatthe UE 106 should have received provisioned credentials. In this regard,for example, bearer activating component 814 can initialize a bearertimer 815 based on activating the one or more data bearers. After thebearer timer 815 expires, the bearers and/or session are released, andthe UE 106 can be required to reestablish the connection with networkentity 304 using provisioned credentials. If the UE 106 did not receivethe credentials, it can reestablish the unauthenticated connection withnetwork entity 304 to obtain the credentials, though it is to beappreciated that a number of attempts to obtain credentials may belimited for a specific UE 106 over a period of time.

For example, where the UE 106 includes an IMEI or other identifier inconnection requests for provisioning, bearer activating component 814can track a number of requests for a given UE based on its identifierover a period of time, and where the number of requests achieves athreshold within a period of time or otherwise, bearer activatingcomponent 814 can reject the bearer establishment for the UE 106, and/orconnection establishing component 318 can reject the initial connectionestablishment request before bearer establishment would occur. Inaddition, in an example, it is to be appreciated that UE 106 canindicate to the network entity 304 that credentials are successfullyreceived and/or that the authenticated connection is successfullyestablished, which may prompt the bearer activating component 814 torelease the one or more data bearers and/or gateway communicatingcomponent 812 to release the session with the gateway.

FIG. 12 illustrates an example system 1200 depicting message flowbetween a UE 106, eNB 108, MME 112, SGW/PGW 110, OSU server 130, and AAA122 in accordance with aspects described with respect to FIGS. 8-11above. At 1202, UE 106 establishes an RRC connection with eNB 108. Asdescribed, this can be an unauthenticated RRC connection for obtainingprovisioning of credentials for accessing services provided by thenetwork. UE 106 obtains, via SDP query/response, network authenticationtype and information regarding OSU server 130, which may be a supportedprovisioning server, as described above. This may be optionallyperformed (a) with MME 112 over NAS at 1204, (b) with eNB 108 over RRCat 1206, etc. In either case, UE 106 can perform an attach procedureindicating that the UE 106 is seeking online provisioning ofcredentials. This may be indicated by the use of a specific known APN,e.g. “Provisioning,” the use of a known specific IMSI (e.g., all zeros),the use of an APN created based on the OSU service provider, etc. It canadditionally or alternatively be indicated by defining a new evolvedpacket system (EPS) attach type value: “EPS attach for provisioning.” Itmay also be indicated by the transmitting a new NAS message for thepurpose of provisioning, by including a new IE indicating theprovisioning server, a provisioning server index or identifier, a typeof provisioning server, or a default provisioning server, etc., and/orthe like.

At 1208, MME 112 proceeds with establishing a non-authenticatednon-secure PDN connection with a SGW/PGW 110, where the connection isrestricted to provisioning. In this regard, MME 112 can send a CreateSession Request message to the SGW/PGW 110 indicating that the sessionis for the purpose of provisioning. The message may also include theservice provider from which provisioning is allowed, and/or specificinformation about the allowed provisioning server(s), e.g., DNS name,internet protocol (IP) address, etc. The SGW/PGW 110 can accept therequest by sending a Create Session Response to MME 112. MME 112 canthen initiate default EPS bearer activation towards the eNB 108 and UE106. MME 112 may start a timer (e.g., bearer timer 815) based oninitiating the EPS bearer activation, upon expiration of which the MME112 may release the connection. For example, when MME 112 releases theconnection, MME 112 may request the UE 106 to detach and reattach sothat the UE 106 uses the provisioned credentials. Alternatively, thetimer expiration may be interpreted as UE 106 failure to obtaincredentials with the OSU server 130. If the provisioning was donethrough the use of an OSU service provider specific APN, the MME 112 mayreject connection requests to such APN after a number of attempts. Inany case, UE 106 can identify itself in the attach message, even if itis not using an identifier that is valid for registration in thisnetwork. For example, UE 106 may identify itself by using its IMEI, anew type of identity value (similar to media access control (MAC)address) for LTE-U capable devices, etc., in the EPS mobile identity IEin the attach request.

At 1210, once the UE 106 is attached to the SGW/PGW 110 and thus has oneor more data bearers with eNB 108 for communicating with MME 112,SGW/PGW 110, etc., UE 106 initiates the Subscription selection andcredentials provisioning with the OSU Server 130, which may occur oversecure mechanism, such as HTTPS, OMA DM SOAP XML, etc. Upon successfulprovisioning of the UE 106, the OSU server 130 may update other networknodes about this new subscription information (e.g., AAA 122 in ahotspot deployment, an HSS in an offload deployment, etc.) at 1212. At1214, the RRC connection can be released, and at 1216, UE 106 canestablish a new RRC connection and can perform an attach procedure withthe network using the new set of credentials. The AAA 122 canauthenticate the UE 106 based on the credentials at 1218, as describedherein.

Turning now to FIGS. 13-15, additional aspects of the present apparatusand method are depicted with reference to one or more components and oneor more methods that may perform the actions or functions describedherein. Although the operations described below in FIGS. 14 and 15 arepresented in a particular order and/or as being performed by an examplecomponent, it should be understood that the ordering of the actions andthe components performing the actions may be varied, depending on theimplementation. Moreover, it should be understood that the followingactions or functions may be performed by a specially-programmedprocessor, a processor executing specially-programmed software orcomputer-readable media, or by any other combination of a hardwarecomponent and/or a software component capable of performing thedescribed actions or functions.

FIG. 13 depicts a system 1300 for requesting authentication foraccessing a wireless network. System 1300 includes a UE 106 thatcommunicates with a network entity 304 to request authentication foraccessing network services, as described herein. Network entity 304 cancommunicate with one or more network components to authenticate the UE106, such as a AAA server 122.

UE 106 may include a network/service connecting component 306, asdescribed, for determining network identification information and/orservice identification information related to network entity 304. Forexample, network/service connecting component 306 may include aconnection establishing component 312 for establishing a connection withthe network entity based at least in part on the network identificationinformation, a service querying component 314 for querying the networkentity for a serving provider related thereto, as described herein, anauthentication requesting component 1310 for determining a type ofauthentication to use in accessing a network, and/or an optional keyderiving component 1312 for performing a keying function from receivedauthentication information to derive specific integrity protection andencryption keys in communicating with the network. It is to beappreciated that the network/service connecting component 306 mayinclude additional components, which may be omitted from this Figure forease of explanation.

Network entity 304 may include a network/service decoupling component308 for separately signaling network identification information and/orrelated service identification information, as described.Network/service decoupling component 308 may include a connectionestablishing component 318 for facilitating connection establishmentwith one or more UEs, a service provisioning component 320 forprovisioning service information (e.g., an indication of a serviceprovider) to the one or more UEs, an authenticating component 1314 forreceiving or otherwise indicating a type of authentication for accessingthe network entity, and/or an optional key deriving component 1316 forderiving similar specific integrity protection and encryption keys basedon an encryption function performed on received authenticationinformation. It is to be appreciated that the network/service decouplingcomponent 308 may include additional components, which may be omittedfrom this Figure for ease of explanation.

FIG. 14 depicts an example method 1400 for requesting authentication foraccessing network services. FIG. 15 illustrates an example method 1500for performing authentication with a UE to provide network services. Asdescribed above, UE 106 includes a connection establishing component 312for establishing a connection with network entity 304, which hasconnection establishing component 318 for performing the connectionestablishment with UE 106. An initial connection can be established asan unauthenticated connection to allow the UE 106 to obtain informationregarding network services and/or related subscription providerinformation supported by a network to which network entity 304 relates.In this regard, service querying component 314 can query the networkentity 304 for the information, and service provisioning component 320can communicate related information to the UE 106.

Method 1400 of FIG. 14 includes, at Block 1402, determining to performEAP authentication with a network. For example, authenticationrequesting component 1310 can determine to perform EAP authenticationwith the network (e.g., with network entity 304). For example, servicequerying component 314 (FIG. 13) can determine that service informationreceived from the network entity 304 indicates an authentication typefor network services. In another example, service querying component 314can determine whether credentials stored in the UE 106 for service orsubscription provider information received from the network entity 304relate to EAP authentication and/or a certain type of EAPauthentication, etc. In yet another example, authentication requestingcomponent 1310 can determine to perform EAP authentication based on atype of the network or other type identifier (e.g., as received in abroadcast message, such as SIB, as described, and/or based oninformation received from the network entity 304 in a dedicatedmessage). For example, the network type may relate to hotspot, offload,etc., and service querying component 314 may determine to perform EAPauthentication for hotspot network types.

Method 1400 also includes, at Block 1404, transmitting a registrationmessage over a NAS layer to the network indicating that EAPauthentication is to be performed. For instance, connection establishingcomponent 312 can generate and transmit the registration message overthe NAS layer to the network (e.g., network entity 304) indicating thatEAP authentication is to be performed. For example, the registrationmessage may include an attach request, tracking area update request, anew NAS message defined for indicating EAP authentication, etc. Inaddition, for example, the registration message may include anindication that EAP is to be performed such as a new value for EPSattach type IE, a specific APN, a new IE indicating EAP authentication,a specific IMSI or other UE identifier, etc. Moreover, for example, theregistration message can be a generic NAS transport specifying “EAP,” anEAP request NAS message, etc.

Method 1500 of FIG. 15 includes, at Block 1502, receiving a registrationmessage from a UE that specifies that EAP authentication is to beperformed. Thus, connection establishing component 318 of network entity304 can receive the registration message from the UE (e.g., UE 106) thatspecifies that EAP authentication is to be performed. Connectionestablishing component 318 can determine this message indicates that EAPauthentication is to be performed based at least in part on one of themessage aspects described above, such as a certain type of NAS message,certain indicators within the message (e.g., a certain EPS attach typevalue, a certain APN, a new IE for EAP authentication, a certain IMSI,etc.), and/or the like. Method also includes, at Block 1504, sending amessage to the UE indicating EAP authentication can be initiated. Inthis regard, connection establishing component 318 can transmit themessage to the UE (e.g., UE 106) indicating EAP authentication can beinitiated. Moreover, for example, the response message can be a genericNAS transport specifying “EAP,” an EAP response NAS message, etc.

Method 1400 includes, at Block 1406, receiving a response indicatingwhether EAP authentication can be initiated. Connection establishingcomponent 312 can receive the response indicating whether EAPauthentication can be initiated (e.g., from network entity 304). Method1400 also includes, at Block 1408, indicating a type of EAPauthentication by using EAP signaling with the network. For example,authentication requesting component 1310 can determine a type of EAPauthentication, and can indicate the type to the network (e.g., by EAPsignaling over the connection established by connection establishingcomponent 312). In one example, authentication requesting component 1310can determine the type of EAP authentication based on a type of thenetwork as received in a broadcast or dedicated message from networkentity 304, information regarding a services provided by the networkand/or subscription providers supported by the network as received byservice querying component 314, and/or the like. For example, the EAPauthentication type can include at least one of EAP-transport layersecurity (EAP-TLS), EAP-tunneled TLS (EAP-TTLS), EAP-authentication andkey agreement (EAP-AKA), EAP-AKA prime (EAP-AKA′), EAP-protected EAP(EAP-PEAP), EAP TLS MS challenge-handshake authentication protocolversion 2 (EAP TLS MSCHAPv2), EAP-generic token card (EAP-GTC), and/orthe like.

Method 1500 includes, at Block 1506, negotiating the type of EAPauthentication to be used in authenticating the UE. Authenticatingcomponent 1314 can negotiate the type of EAP authentication to be usedin authenticating the UE (e.g., UE 106). Thus, for example,authenticating component 1314 can receive the EAP authentication typeindicated by UE 106, and can accept the type and/or can respond withanother EAP authentication type to UE 106 (e.g., where the typeindicated by the UE 106 is not supported). Method 1500 also optionallyincludes, at Block 1508, performing EAP authentication of the UE with anAAA server. Thus, for example, once the EAP type is agreed upon by theUE 106 and network entity 304, authenticating component 1314 can performEAP authentication of the UE (e.g., UE 106) with the AAA server (e.g.,AAA server 122). For example, this can include communicating relatedcredentials received in EAP messages from the UE 106 to AAA server 122.In one example, network entity 304 establishes an EAP Radius/Diameterexchange with AAA server 122 (e.g., via a gateway or otherwise) forperforming authentication for the UE 106. Once the authentication isperformed, authenticating component 1314 can communicate anauthentication status back to the UE 106, which is received byauthentication requesting component 1310 and used to determine whetherto communicate with the network.

Method 1400 may include, at Block 1410, deriving keys based on the EAPauthentication. Thus, for example, UE 106 may include a key derivingcomponent 1312 for deriving keys based on the EAP authentication. Thismay include performing a keying function from received authenticationinformation to derive specific integrity protection and encryption keysto utilize in subsequent communications with network entity 304 (e.g.,over eNB 108). Method 1500 can similarly include, at Block 1510,deriving keys based on the EAP authentication. Thus, for example,network entity 304 may also include a key deriving component 1316 forderiving keys based on the EAP authentication. This may similarlyinclude specific integrity protection and encryption keys based on anencryption function performed on received authentication information. Inone example, key deriving component 1316 provides the keys and/orrelated information to an eNB 108 or other network component tofacilitate ensuring UE 106 is authenticated to access network entity 304via the eNB 108 or other network component.

FIGS. 16 and 17 illustrate example systems 1600 and 1700 depictingmessage flow between a UE 106, eNB 108, MME 112 (or MME/HSS 1702 in FIG.17), SGW/PGW 110, AAA 122 in accordance with aspects described withrespect to FIGS. 13-15 above. In FIG. 16, at 1602, the UE 106establishes an RRC connection with eNB 108 for setting up anauthenticated connection with network. At 1604, UE 106 sends an AttachRequest providing an indication that EAP authentication is required toMME 112 (or MME/HSS 1702 in FIG. 17). In order to do so, for example, anew value may be defined for EPS attach type IE: “EPS attach with EAPauthentication.” Alternatively, in an example, this can be indicatedusing a specific APN, or a new IE indicating EAP authentication isexpected. Moreover, in another example, a new type of Attach messagecould be used or a specific IMSI or UE identifier type that the UE canprovide and is interpreted by the MME 112 (or MME/HSS 1702 in FIG. 17)as indicating the need to use EAP so that no new IEs are needed.

Accordingly, EAP authentication is performed over generic NAS transportat 1606 and 1608, where EAP Radius/Diameter exchanges can occur betweenMME 112 and AAA 122 at 1608. In FIG. 17, an example EAP authenticationusing EAP-TLS is shown at 1704. In either case, for example, Generic NASTransport with EAP type can be used to exchange EAP signaling. Uponsuccessful authentication, the UE 106 and the MME 112 (or MME/HSS 1702in FIG. 17) derive the LTE keying material from the EAP keying materialthrough a KDF (key Derivation Function), at 1610 and 1612 respectively.Alternatively, in an example, a new NAS EAP request/response pair ofmessages may be used. Additionally, for example, MME 112 may provisionthe eNB 108 with the keys for utilizing in communicating with UE 106.Upon successful authentication, MME 112 (or MME/HSS 1702 in FIG. 17)triggers the PDN connection establishment for UE 106 at 1614, and cansend an attach accept message to the UE 106 at 1616.

Referring to FIG. 18, a multiple access wireless communication systemaccording to one embodiment is illustrated. An access point 1800 (AP)includes multiple antenna groups, one including 1804 and 1806, anotherincluding 1808 and 1810, and an additional including 1812 and 1814. InFIG. 18, only two antennas are shown for each antenna group, however,more or fewer antennas can be utilized for each antenna group. Inaddition, AP 1800 can include a network/service decoupling component308, as described herein, to provide network identification informationand service identification information to one or more UEs (e.g., accessterminals), where the service identification information may includesupported subscription providers, information for obtaining credentials,etc. Access terminal 1816 (AT) is in communication with antennas 1812and 1814, where antennas 1812 and 1814 transmit information to accessterminal 1816 over forward link 1820 and receive information from accessterminal 1816 over reverse link 1818. Access terminal 1822 is incommunication with antennas 1804 and 1806, where antennas 1804 and 1806transmit information to access terminal 1822 over forward link 1826 andreceive information from access terminal 1822 over reverse link 1824. Ina FDD system, communication links 1818, 1820, 1824 and 1826 can usedifferent frequency for communication. For example, forward link 1820can use a different frequency then that used by reverse link 1818. Inaddition, ATs 1816 and/or 1822 can include a network/service connectingcomponent 306, as described herein, to request information regardingnetwork services, supported subscription providers, credentials, etc.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access point. In theembodiment, antenna groups each are designed to communicate to accessterminals in a sector of the areas covered by access point 1800.

In communication over forward links 1820 and 1826, the transmittingantennas of access point 1800 utilize beamforming in order to improvethe signal-to-noise ratio of forward links for the different accessterminals 1816 and 1822. Also, an access point using beamforming totransmit to access terminals scattered randomly through its coveragecauses less interference to access terminals in neighboring cells thanan access point transmitting through a single antenna to all its accessterminals.

Moreover, access terminals 1816 and 1822 can provide UE functionality toobserve network services advertised by access point 1800, receivedprovisioned credentials, perform authentication based on thecredentials, etc., as described herein.

FIG. 19 is a block diagram of an embodiment of a transmitter system 1910(also known as the access point) and a receiver system 1950 (also knownas access terminal) in a MIMO system 1900. At the transmitter system1910, traffic data for a number of data streams is provided from a datasource 1912 to a transmit (TX) data processor 1914. In addition, it isto be appreciated that transmitter system 1910 and/or receiver system1950 can employ the systems (FIGS. 1-3, 6, 8, 12, 13, 16, and 17) and/ormethods (FIGS. 4, 5, 7, 9-11, 14, and 15) described herein to facilitatewireless communication there between. For example, components orfunctions of the systems and/or methods described herein can be part ofa memory 1932 and/or 1972 or processors 1930 and/or 1970 describedbelow, and/or can be executed by processors 1930 and/or 1970 to performthe disclosed functions.

In an example, transmitter system 1910 may include an eNB, and may thusinclude a network/service decoupling component 308, as described herein,to provide network identification information and service identificationinformation to one or more UEs (e.g., access terminals), where theservice identification information may include supported subscriptionproviders, information for obtaining credentials, etc. Thenetwork/service decoupling component 308 may be communicatively coupledwith one or more processors 1930 for executing functions associated withthe component 308 and/or components thereof, as described herein (e.g.,in FIGS. 3, 8, 13, etc.), such to perform methods 500 (FIG. 5), 1000(FIG. 10), 1500 (FIG. 15), etc. In another example, receiver system 1950may include a UE, and may thus include a network/service connectingcomponent 306, as described herein, to request information regardingnetwork services, supported subscription providers, credentials, etc.The network/service connecting component 306 may be communicativelycoupled with one or more processors 1970 for executing functionsassociated with the component 306 and/or components thereof, asdescribed herein (e.g., in FIGS. 3, 8, 13, etc.), such to performmethods 400 (FIG. 4), 700 (FIG. 7), 9000 (FIG. 9), 1400 (FIG. 14), etc.

In an embodiment, each data stream is transmitted over a respectivetransmit antenna. TX data processor 1914 formats, codes, and interleavesthe traffic data for each data stream based on a particular codingscheme selected for that data stream to provide coded data.

The coded data for each data stream can be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and can be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (e.g., symbol mapped) basedon a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream can be determined byinstructions performed by processor 1930.

The modulation symbols for all data streams are then provided to a TXMIMO processor 1920, which can further process the modulation symbols(e.g., for OFDM). TX MIMO processor 1920 then provides N_(T) modulationsymbol streams to N_(T) transmitters (TMTR) 1922 a through 1922 t. Incertain embodiments, TX MIMO processor 1920 applies beamforming weightsto the symbols of the data streams and to the antenna from which thesymbol is being transmitted.

Each transmitter 1922 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. N_(T)modulated signals from transmitters 1922 a through 1922 t are thentransmitted from N_(T) antennas 1924 a through 1924 t, respectively.

At receiver system 1950, the transmitted modulated signals are receivedby N_(R) antennas 1952 a through 1952 r and the received signal fromeach antenna 1952 is provided to a respective receiver (RCVR) 1954 athrough 1954 r. Each receiver 1954 conditions (e.g., filters, amplifies,and downconverts) a respective received signal, digitizes theconditioned signal to provide samples, and further processes the samplesto provide a corresponding “received” symbol stream.

An RX data processor 1960 then receives and processes the N_(R) receivedsymbol streams from N_(R) receivers 1954 based on a particular receiverprocessing technique to provide N_(T) “detected” symbol streams. The RXdata processor 1960 then demodulates, deinterleaves, and decodes eachdetected symbol stream to recover the traffic data for the data stream.The processing by RX data processor 1960 is complementary to thatperformed by TX MIMO processor 1920 and TX data processor 1914 attransmitter system 1910.

A processor 1970 periodically determines which pre-coding matrix to use.Processor 1970 formulates a reverse link message comprising a matrixindex portion and a rank value portion.

The reverse link message can comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message is then processed by a TX data processor 1938,which also receives traffic data for a number of data streams from adata source 1936, modulated by a modulator 1980, conditioned bytransmitters 1954 a through 1954 r, and transmitted back to transmittersystem 1910.

At transmitter system 1910, the modulated signals from receiver system1950 are received by antennas 1924, conditioned by receivers 1922,demodulated by a demodulator 1940, and processed by a RX data processor1942 to extract the reserve link message transmitted by the receiversystem 1950. Processor 1930 then determines which pre-coding matrix touse for determining the beamforming weights then processes the extractedmessage.

Processors 1930 and 1970 can direct (e.g., control, coordinate, manage,etc.) operation at transmitter system 1910 and receiver system 1950,respectively. Respective processors 1930 and 1970 can be associated withmemory 1932 and 1972 that store program codes and data. For example,processors 1930 and 1970 can perform functions described herein withrespect to UE 106, eNB 108, MME 112, network entity 304, etc., and/orcan operate one or more of the corresponding components. Similarly,memory 1932 and 1972 can store instructions for executing thefunctionality or components, and/or related data.

The various illustrative logics, logical blocks, modules, components,and circuits described in connection with the embodiments disclosedherein may be implemented or performed with a general purpose processor,a digital signal processor (DSP), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA) or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Additionally, at least oneprocessor may comprise one or more modules operable to perform one ormore of the steps and/or actions described above. An exemplary storagemedium may be coupled to the processor, such that the processor can readinformation from, and write information to, the storage medium. In thealternative, the storage medium may be integral to the processor.Further, in some aspects, the processor and the storage medium mayreside in an ASIC. Additionally, the ASIC may reside in a user terminal.In the alternative, the processor and the storage medium may reside asdiscrete components in a user terminal.

In one or more aspects, the functions, methods, or algorithms describedmay be implemented in hardware, software, firmware, or any combinationthereof. If implemented in software, the functions may be stored ortransmitted as one or more instructions or code on a computer-readablemedium, which may be incorporated into a computer program product.Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage medium may be anyavailable media that can be accessed by a computer. By way of example,and not limitation, such computer-readable media can comprise RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tocarry or store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, substantiallyany connection may be termed a computer-readable medium. For example, ifsoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs usually reproduce data optically withlasers. Combinations of the above should also be included within thescope of computer-readable media.

While the foregoing disclosure discusses illustrative aspects and/orembodiments, it should be noted that various changes and modificationscould be made herein without departing from the scope of the describedaspects and/or embodiments as defined by the appended claims.Furthermore, although elements of the described aspects and/orembodiments may be described or claimed in the singular, the plural iscontemplated unless limitation to the singular is explicitly stated.Additionally, all or a portion of any aspect and/or embodiment may beutilized with all or a portion of any other aspect and/or embodiment,unless stated otherwise.

What is claimed is:
 1. A method for detecting wireless network services,comprising: determining, by a user equipment (UE), a network identifierin a broadcast message received from a network entity; establishing aconnection with a network related to the network entity based at leastin part on the network identifier; and querying, using the connection,the network entity for information related to services available at thenetwork.
 2. The method of claim 1, further comprising determining a typeof the network, wherein querying the network is based at least in parton the type of the network.
 3. The method of claim 2, wherein the typeof the network comprises a hotspot or an offload network, and whereindetermining the type of the network is based at least in part on thenetwork identifier.
 4. The method of claim 1, further comprisingreceiving subscription information of the network in response toquerying the network entity, wherein the subscription informationidentifies one or more subscription providers supported by the network.5. The method of claim 4, further comprising determining a set ofcredentials for establishing an authenticated connection with thenetwork based at least in part on the one or more subscriptionproviders.
 6. The method of claim 5, further comprising establishing aradio resource control (RRC) layer connection with at least one of theone or more subscription providers over the network at least in part byspecifying the set of credentials.
 7. The method of claim 1, whereinquerying the network entity comprises querying for an icon related toone or more of the services available at the network.
 8. The method ofclaim 1, wherein querying the network entity comprises transmitting aradio resource control (RRC) message or a non-access stratum (NAS)message to the network entity to query for the information.
 9. Themethod of claim 1, wherein the network identifier comprises at least oneof a public land mobile network (PLMN) identifier (ID), a closedsubscriber group (CSG) ID, an access network ID, a public network ID, ora private network ID.
 10. The method of claim 1, wherein the broadcastmessage comprises a system information block (SIB) that indicates thenetwork identifier in an information element.
 11. The method of claim 1,further comprising receiving an indication from the network entity thatthe query for the information is supported by the network entity,wherein querying the network entity is based at least in part onreceiving the indication.
 12. The method of claim 1, wherein the networkentity is an evolved Node B (eNB) or a mobility management entity (MME).13. An apparatus for detecting wireless network services, comprising: anidentifier determining component configured to determine a networkidentifier in a broadcast message received from a network entity; aconnection establishing component configured to establish a connectionwith a network related to the network entity based at least in part onthe network identifier; and a service querying component configured toquery, using the connection, the network entity for information relatedto services available at the network.
 14. The apparatus of claim 13,wherein the connection establishing component is further configured todetermine a type of the network, and wherein the service queryingcomponent is configured to query the network based at least in part onthe type of the network.
 15. The apparatus of claim 14, wherein the typeof the network comprises a hotspot or an offload network, and whereinthe connection establishing component is configured to determine thetype of the network based at least in part on the network identifier.16. The apparatus of claim 13, wherein the service querying component isfurther configured to receive subscription information of the network inresponse to querying the network entity, wherein the subscriptioninformation identifies one or more subscription providers supported bythe network.
 17. The apparatus of claim 16, wherein the connectionestablishing component is further configured to determine a set ofcredentials for establishing an authenticated connection with thenetwork based at least in part on the one or more subscriptionproviders.
 18. The apparatus of claim 17, wherein the connectionestablishing component is further configured to establish a radioresource control (RRC) layer connection with at least one of the one ormore subscription providers over the network at least in part byspecifying the set of credentials.
 19. The apparatus of claim 13,wherein the service querying component is configured to query thenetwork entity for an icon related to one or more of the servicesavailable at the network.
 20. The apparatus of claim 13, wherein theservice querying component is configured to query the network entity atleast in part by transmitting a radio resource control (RRC) message ora non-access stratum (NAS) message to the network entity to query forthe information.
 21. The apparatus of claim 13, wherein the networkidentifier comprises at least one of a public land mobile network (PLMN)identifier (ID), a closed subscriber group (CSG) ID, an access networkID, a public network ID, or a private network ID.
 22. The apparatus ofclaim 13, wherein the broadcast message comprises a system informationblock (SIB) that indicates the network identifier in an informationelement.
 23. The apparatus of claim 13, wherein the service queryingcomponent is configured to receive an indication from the network entitythat the query for the information is supported by the network entity,and query the network entity based at least in part on receiving theindication.
 24. The apparatus of claim 13, wherein the network entity isan evolved Node B (eNB) or a mobility management entity (MME).
 25. Anapparatus for detecting wireless network services, comprising: means fordetermining a network identifier in a broadcast message received from anetwork entity; means for establishing a connection with a networkrelated to the network entity based at least in part on the networkidentifier; and means for querying, using the connection, the networkentity for information related to services available at the network. 26.The apparatus of claim 25, wherein the means for establishing theconnection determines a type of the network, and wherein the means forquerying queries the network based at least in part on the type of thenetwork.
 27. The apparatus of claim 26, wherein the type of the networkcomprises a hotspot or an offload network, and wherein the means forestablishing the connection determines the type of the network based atleast in part on the network identifier.
 28. The apparatus of claim 25,wherein the means for querying receives subscription information of thenetwork in response to querying the network entity, wherein thesubscription information identifies one or more subscription providerssupported by the network.
 29. The apparatus of claim 28, wherein themeans for establishing the connection determines a set of credentialsfor establishing an authenticated connection with the network based atleast in part on the one or more subscription providers.
 30. Theapparatus of claim 29, wherein the means for establishing the connectionestablishes a radio resource control (RRC) layer connection with atleast one of the one or more subscription providers over the network atleast in part by specifying the set of credentials.
 31. The apparatus ofclaim 25, wherein the means for querying queries the network entity foran icon related to one or more of the services available at the network.32. The apparatus of claim 25, wherein the means for querying queriesthe network entity at least in part by transmitting a radio resourcecontrol (RRC) message or a non-access stratum (NAS) message to thenetwork entity to query for the information.
 33. The apparatus of claim25, wherein the network identifier comprises at least one of a publicland mobile network (PLMN) identifier (ID), a closed subscriber group(CSG) ID, an access network ID, a public network ID, or a privatenetwork ID.
 34. The apparatus of claim 25, wherein the broadcast messagecomprises a system information block (SIB) that indicates the networkidentifier in an information element.
 35. The apparatus of claim 25,wherein the means for querying receives an indication from the networkentity that the query for the information is supported by the networkentity, and queries the network entity based at least in part onreceiving the indication.
 36. The apparatus of claim 25, wherein thenetwork entity is an evolved Node B (eNB) or a mobility managemententity (MME).
 37. A computer-readable medium for detecting wirelessnetwork services, comprising: code for determining a network identifierin a broadcast message received from a network entity; code forestablishing a connection with a network related to the network entityat least in part on the network identifier; and code for querying, usingthe connection, the network entity for information related to servicesavailable at the network.
 38. The computer-readable medium of claim 37,wherein the code for establishing the connection determines a type ofthe network, and wherein the code for querying queries the network basedat least in part on the type of the network.
 39. The computer-readablemedium of claim 38, wherein the type of the network comprises a hotspotor an offload network, and wherein the code for establishing theconnection determines the type of the network based at least in part onthe network identifier.
 40. The computer-readable medium of claim 37,wherein the code for querying receives subscription information of thenetwork in response to querying the network entity, wherein thesubscription information identifies one or more subscription providerssupported by the network.
 41. The computer-readable medium of claim 40,wherein the code for establishing the connection determines a set ofcredentials for establishing an authenticated connection with thenetwork based at least in part on the one or more subscriptionproviders.
 42. The computer-readable medium of claim 41, wherein thecode for establishing the connection establishes a radio resourcecontrol (RRC) layer connection with at least one of the one or moresubscription providers over the network at least in part by specifyingthe set of credentials.
 43. The computer-readable medium of claim 37,wherein the code for querying queries the network entity for an iconrelated to one or more of the services available at the network.
 44. Thecomputer-readable medium of claim 37, wherein the code for queryingqueries the network entity at least in part by transmitting a radioresource control (RRC) message or a non-access stratum (NAS) message tothe network entity to query for the information.
 45. Thecomputer-readable medium of claim 37, wherein the network identifiercomprises at least one of a public land mobile network (PLMN) identifier(ID), a closed subscriber group (CSG) ID, an access network ID, a publicnetwork ID, or a private network ID.
 46. The computer-readable medium ofclaim 37, wherein the broadcast message comprises a system informationblock (SIB) that indicates the network identifier in an informationelement.
 47. The computer-readable medium of claim 37, wherein the codefor querying receives an indication from the network entity that thequery for the information is supported by the network entity, andqueries the network entity based at least in part on receiving theindication.
 48. The computer-readable medium of claim 37, wherein thenetwork entity is an evolved Node B (eNB) or a mobility managemententity (MME).
 49. A method for advertising wireless network services,comprising: broadcasting a message including a network identifier,wherein the network identifier indicates a type of network; establishinga connection with one or more user equipments (UEs); and providingservice information to the one or more UEs based at least in part on aservice query.
 50. The method of claim 49, wherein the connection withthe one or more UEs includes a radio resource control (RRC) layerconnection or a non-access stratum (NAS) connection.
 51. The method ofclaim 49, wherein the connection is an unauthenticated connection. 52.The method of claim 49, wherein the service information comprisesinformation of one or more supported subscription providers.
 53. Themethod of claim 49, further comprising establishing an authenticatedconnection with the one or more UEs based at least in part on theservice information.
 54. An apparatus for advertising wireless networkservices, comprising: an identifier broadcasting component configured tobroadcast a message including a network identifier, wherein the networkidentifier indicates a type of network; a connection establishingcomponent configured to establish a connection with one or more userequipments (UEs); and a service provisioning component configured toprovide service information to the one or more UEs based at least inpart on a service query.
 55. The apparatus of claim 54, wherein theconnection with the one or more UEs includes a radio resource control(RRC) layer connection or a non-access stratum (NAS) connection.
 56. Theapparatus of claim 54, wherein the connection is an unauthenticatedconnection.
 57. The apparatus of claim 54, wherein the serviceinformation comprises information of one or more supported subscriptionproviders.
 58. The apparatus of claim 54, wherein the connectionestablishing component is further configured to establish anauthenticated connection with the one or more UEs based at least in parton the service information.
 59. An apparatus for advertising wirelessnetwork services, comprising: means for broadcasting a message includinga network identifier, wherein the network identifier indicates a type ofnetwork; means for establishing a connection with one or more userequipments (UEs); and means for providing service information to the oneor more UEs based at least in part on a service query.
 60. The apparatusof claim 59, wherein the connection with the one or more UEs includes aradio resource control (RRC) layer connection or a non-access stratum(NAS) connection.
 61. The apparatus of claim 59, wherein the connectionis an unauthenticated connection.
 62. The apparatus of claim 59, whereinthe service information comprises information of one or more supportedsubscription providers.
 63. The apparatus of claim 59, wherein the meansfor establishing the connection establishes an authenticated connectionwith the one or more UEs based at least in part on the serviceinformation.
 64. A computer-readable medium for advertising wirelessnetwork services, comprising: code for causing at least one computer tobroadcast a message including a network identifier, wherein the networkidentifier indicates a type of network; code for causing the at leastone computer to establish a connection with one or more user equipments(UEs); and code for causing the at least one computer to provide serviceinformation to the one or more UEs based at least in part on a servicequery.
 65. The computer-readable medium of claim 64, wherein theconnection with the one or more UEs includes a radio resource control(RRC) layer connection or a non-access stratum (NAS) connection.
 66. Thecomputer-readable medium of claim 64, wherein the connection is anunauthenticated connection.
 67. The computer-readable medium of claim64, wherein the service information comprises information of one or moresupported subscription providers.
 68. The computer-readable medium ofclaim 64, wherein the code for establishing the connection establishesan authenticated connection with the one or more UEs based at least inpart on the service information.